feat: add scope control for password complexity rules#415
Open
rohasmsk wants to merge 1 commit into
Open
Conversation
Allow admins to selectively apply complexity rules to user account passwords, public link passwords, or both via two new checkboxes in the security settings.
|
Maksim Martynov seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account. You have signed the CLA already but the status is still pending? Let us recheck it. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
admin security settings: Apply to user account passwords and
Apply to public link passwords (both enabled by default —
no change in behavior for existing installations)
chars) are now skipped for the unchecked scope; password history,
expiration and force-change-on-first-login rules are unaffected and
continue to apply to user accounts only
Motivation
Workaround for #359
This change provides a workaround for #359.
Installations using OpenID Connect (or other external identity
providers) can now disable complexity checks for user account passwords,
since those users authenticate via their IdP which enforces its own
password policies. Applying ownCloud's complexity rules on top is
redundant and causes friction. At the same time, complexity rules for
public link passwords remain fully functional.